5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
- Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-5: The Appx ILF Debugger

Clearing Out Break Points


To clear out hard-coded break points (TRAP statements), you can invoke the ILF editor and delete them. Alternatively, there are processes on the Utilities, Toolbox menu in Application Design that 'Turn All TRAPs Off' and 'Turn All TRAPs On' in a given application. The first process converts TRAP statements into 'tftft TRAP' comments (where 'tftft' is replaced by the actual T/F indicators if any are present on the TRAP statement) and the second process converts the comments back to TRAP statements. Remember that TRAP statements are not intercepted in the end user environment, so ordinary users will never be aware of their existence.

If TRAP statements are not deleted or turned off, they remain a permanent part of a routine. The break points that you set dynamically within the debugger by using Select (F3) are automatically cleared when you leave the debugger. You must reactivate any dynamic break points when you return to the debugger.

Application Design Manual                                         "Powered by Appx Software"

605

©2006 By APPX Software, Inc. All Rights Reserved